Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kie-kogito-serverless-operator-361: Add data-index and job service st… #377

Merged
merged 1 commit into from
Feb 2, 2024

Conversation

wmedvede
Copy link
Contributor

…artupProbes to the workflow Deployment

Description of the change:

Motivation for the change:

Checklist

  • Add or Modify a unit test for your change
  • Have you verified that tall the tests are passing?
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

Copy link
Member

@ricardozanini ricardozanini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! But I'm missing the startupProbe in the workflow container. 😅

controllers/platform/services/services.go Outdated Show resolved Hide resolved
@wmedvede
Copy link
Contributor Author

Thank you! But I'm missing the startupProbe in the workflow container. 😅

this startupProbe is already being set here:

@ricardozanini
Copy link
Member

@wmedvede can u rebase?

@wmedvede wmedvede force-pushed the kie-kogito-serverless-operator-361 branch from 02aebd9 to 5b2d2ad Compare February 1, 2024 08:56
@wmedvede wmedvede force-pushed the kie-kogito-serverless-operator-361 branch from 5b2d2ad to 3ad417d Compare February 1, 2024 20:09
@wmedvede wmedvede merged commit 47c73db into apache:main Feb 2, 2024
4 checks passed
rgdoliveira pushed a commit to rgdoliveira/kogito-serverless-operator that referenced this pull request Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants